home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
The CICA Windows Explosion!
/
The CICA Windows Explosion! - Disc 2.iso
/
nt
/
ntkb.zip
/
NTKB.EXE
/
Q110
/
2
/
55.TXT
< prev
next >
Wrap
Text File
|
1994-01-24
|
4KB
|
97 lines
DOCUMENT:Q110255 20-JAN-1994 [W_NT]
TITLE :Performance Drops During Large File Copy
PRODUCT :Windows NT
PROD/VER:3.10
OPER/SYS:WINDOWS
KEYWORDS:
--------------------------------------------------------------------------
The information in this article applies to:
- Microsoft Windows NT operating system version 3.1
- Microsoft Windows NT Advanced Server version 3.1
--------------------------------------------------------------------------
SYMPTOMS
========
System performance drops to an unacceptable level while a large file is
being copied.
CAUSE
=====
This problem may be a symptom of a problem with the way that the Server
service interacts with the system cache in certain configurations.
RESOLUTION
==========
You may be able to work around this problem by tuning the server to balance
memory use. To do this, do the following steps:
1. In the Control Panel window, choose the Network icon.
2. From the Installed Network Software box, select Server, and then choose
the Configure button.
3. If either of the options "Maximize Throughput for File Sharing" or
"Maximize Throughput for Network Applications" are currently selected,
you may get better performance during large file copy operations by
selecting the Balance option. If Balance or Minimize Memory Used is
already selected, this article does not apply.
4. If you elected to make a change in Step 3, restart your computer so the
change can take effect.
MORE INFORMATION
================
The two options that are designed to maximize network throughput each
permit the system cache to use more available memory than it would
otherwise. In this situation, the available memory can drop to levels that
result in heavy swapping activity on the hard disks in order to accommodate
requests from user or system applications that may subsequently need to be
swapped into memory.
The cache manager periodically gives up memory that it has allocated so
that the system will never run completely out of memory due to caching
alone. This can happen whenever a file copy operation is complete or when a
threshold value is reached. This means that the problem described above
does not occur if a series of smaller files are copied. The threshold value
for the Balance option is enough higher than the threshold values for the
options designed to maximize throughput that the problem does not occur
there either.
This problem is also more noticeable on computers with lower total physical
memory. When more total physical memory is available, the minimum available
memory threshold is also higher, which can alleviate the problem.
STATUS
======
Microsoft has confirmed this to be a problem in Windows NT and Windows NT
Advanced Server version 3.1. We are researching this problem and will post
new information here in the Microsoft Knowledge Base as it becomes
available.
Additional reference words: 3.10
KBCategory:
KBSubCategory: netsrv
=============================================================================
THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS
PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS
ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES
OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO
EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR
ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL,
CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF
MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE
POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION
OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES
SO THE FOREGOING LIMITATION MAY NOT APPLY.
Copyright Microsoft Corporation 1994.